Skip to main content
TrustRadius
Azure DevOps Server

Azure DevOps Server
Formerly Team Foundation Server

Overview

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

36 people also want pricing

Alternatives Pricing

What is Azure DevOps Services?

Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.

What is CircleCI?

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…

Return to navigation

Product Details

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Azure DevOps Server Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Reviewers rate Usability highest, with a score of 8.7.

The most common users of Azure DevOps Server are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(280)

Attribute Ratings

Reviews

(1-25 of 28)
Companies can't remove reviews or game the system. Here's why
Melissa Bryant | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
The firm as a whole makes use of Azure DevOps Server for project management, with its efficient capability to prioritize and approve project needs. Our IT team uses this top-notch application to streamline project management tasks like code versioning and test script administration and to make sure all of our requirements are met through thorough testing.
  • Simple tracking of progress throughout the project.
  • Perform project management duties with superior ability to set priorities and approve work.
  • In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
  • It doesn't work well with tools from other companies.
  • Improvements can be made to the user interface to make it more natural to use.
  • I also think capacity planning may use some fine-tuning.
Integrating with Visual Studio makes it easy to see where things stand in terms of different projects' requirements, and the product is great for prioritizing and approving changes as they come up. An easy-to-use tracking and testing system ensures that all criteria are met, making this a great tool for project managers trying to keep their projects within their allotted parameters.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We work according to Agile methodology and Azure DevOps Server (formerly known as TMS) helps us to track and follow the progress of our work efficiently. We use it for version control as well as to review backlog. As we are more of a Microsoft-based company, it helps us a lot since all Microsoft products can be integrated effortlessly with Azure DevOps Server which enhances user experience.
  • You can integrate it effortlessly with almost all Microsoft products
  • Supports Agile and can be used for version control
  • Bug tracking
  • Ease of use
  • I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
  • The user interface could have been better
  • Agile boards can be better
Scenarios where Azure DevOps Server is well suited: When the other tools you need to use are also Microsoft products bug tracking version control (although GitHub is better) Agile management backlog management scenarios where Azure DevOps Server is not well suited: When you need to integrate services other than Microsoft owned.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments.
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.
  • Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
  • Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
  • Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
  • Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Managing software development across several phases can be extremely difficult due two it’s complexity. DevOps and CI/CD can help to control this complexity. However, these methodologies need software solutions that suit this agile approach. In this case Microsoft DevOps is the best suite available at the moment. We use Microsoft DevOps end to end to manage the development of a cross-platform mobile application. As said we use the suite end to end. Starting with „Azure Boards“ to derive, document, and manage backlogs; „Azure Repos“ to manage repositories and changes/change requests; ending with automating testing and pipelines with „Azures Testing“ and „Azure Pipeline“. Integration and extensibility features are used for productivity purposes as well. In this way, Azure DevOps brings together all levels of information at code in one single tool. Especially the automation options in the pipeline Tier helped us to automate delivery processes for both platforms (iOS & Android).
  • Integration and Extensibility Features.
  • Pipeline automations.
  • Configuration and flow of change requests workflows.
  • Configuration of Boards (backlogs).
  • Flexibility and ease of use of dashboards.
  • Change logs of items.
  • Expand automation options for iOS pipeline (include further triggers).
  • Mass handling of backlog items could be improved.
The repro Feature “Azure Repros” was especially valuable in our use case as it was very easy to orchestrate the development of several developers via change requests. In this way, tasks/bugs execution was easy to plan and assign via boards and dashboards, and commits were documented in relation to planning objects and reviewed via the four-eye principle. Senior developers were able to oversee and review junior developers' work easily.
Matthew Budram | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
One product to cover the most common engineering activities in tech irrespective of the domain. Whether the team is in medical tech, fintech, aerospace tech, or a business process outsourcing firm, this platform has all the common tools needed in an Agile workspace with extreme collaborations across DevOps, Product, and Engineering. This gives the best centralized toolset, especially if your organization is already a Microsoft-based firm.
  • Version control
  • Requirements definition
  • Secrets library management
  • Continuous integration and deployment
  • Wiki Markdown customization
  • Better Syntax Highlighter in Repository
  • Improvements in Requirements Definition Customization
In my capacity as an architect, the platform gives me the ability to define the architecture within a wiki. I can include details including flow, UML, and ER diagrams in the User Story of Features being defined by the Product Owner, and my engineering team can link the repository pull requests to the story being developed. My Product Owners can now view the business definitions, software architecture, code written, and QA tests performed all on one central platform.
Christopher Sawyer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We are using Azure DevOps [(formerly Team Foundation Server)] in our IT department to help us with Agile software development. It helps us to track code changes with various work items like Tasks and Bugs. It also helps to test, build and deploy those changes to multiple environments. It easily integrates with Visual Studio to create a seamless experience.
  • All-in-one product (don't need a bunch of separate connected products)
  • Integrates easily with other Microsoft products
  • Can use git or its own version control with less steep learning curve
  • More stable than Atlassian products
  • No clear-cut way to track items in a release, especially if they are not code change related
  • Agile boards still lag behind Jira in terms of functionality
  • Bamboo and Confluence have nice features over DevOps Build and Sharepoint
More stable than Atlassian products but not quite as feature rich. I've supported both TFS (now Azure DevOps) and Atlassian products in the past. Nice to have an all-in-one stable suite but you may not have quite as many bells and whistles. I would choose less features over having to restart servers.
Mark Orlando | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Incentivized
We use Azure DevOps to manage and store all our corporate source code and deploy our applications to a string of various environments from development to production. In addition, we use Azure DevOps on a daily basis to manage our agile-based projects. Azure DevOps is used to track and follow the progress of customer support tickets as well. Our business analysts use the Agile Project Management feature to log user stories.
  • Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
  • Our business analysts use its features to document and assign user stories for Agile-based projects.
  • Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
  • For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
  • Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
  • The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
Azure DevOps works great if you spend most of your day in Visual Studio. If you plan on using VS Code, then skip it because Azure DevOps doesn't really work with VS Code. VS Code works with Git. For project management, Azure Dev Ops is okay, but project managers need to provide their team with links to where things are. Additionally, you might be better off using OneNote to document requirements and simply add links to your user stories where developers and testers can read the stories. The Word-like editor in Azure DevOps is extremely primitive.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
TFS is used for ALM of all in house supportive software, development of our flagship product and clinical studies for our latest version. TFS acts as a central hub for requirements, code, tests and reports. It links these facets of the product life cycle together.
  • Linking together all aspects of the application life cycle, from requirements to code to builds and test.
  • Trace-ability of all application life cycle via reports and queries.
  • Automated testing.
  • Flexibility of source code management. Centralized or distributed.
  • Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
  • Capacity planning could be improved.
  • Dot Net framework 260 character path limit is ridiculous.
Team Foundation Server (TFS) is best for large scale enterprise deployments. Not needed for a small company. With the infrastructure investment, TFS can aid large scale software development immensely. TFS is highly customizable, but if you go the route of heavy customization, don't upgrade to the latest version aggressively. Plan to invest in at least one full time TFS administrator. Make sure the users are properly trained.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Our IT department uses Azure DevOps Server to manage all our projects and for software development.
  • Ease to manage code.
  • Compatible with several services.
  • Version control.
  • Need more templates.
  • Can be confusing to use at first.
  • Reporting could be better.
It is well suited for any IT team, provides a great way to manage and track projects. Great for code reviews and bug management.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Source control for application code, for the most part. For database code, it integrates well with Red Gate software. Besides scripting out database schema, Red Gate will even script out static data so it can be source controlled as well within TFS/ADS. My previous employer used TFS/ADS to automate builds and as a ticketing system.
  • It allows you to view the history of any piece of code. Shows the differences. If you are a good 'code archaeologist' you can figure out why things were changed and when.
  • It provides a repository of your code so you can reconstruct it in case of a catastrophe. With code history, you can restore the code as it was before some change that didn't work, was made.
  • The tickets it creates can be linked to the changes in the code. This adds an important element showing causation. This code change resolves or is associated with this ticket which includes the purpose of the change.
  • The way it uses workspaces is non-intuitive. I required help from our resident expert to get TFS set up initially.
  • Don't forget to refresh again and again. Yes, of course, you want the latest changes - you shouldn't have to remember to keep hitting that button.
  • Even though it uses a Microsoft SQL Server database to store its data, it uses the database in a non-standard way. Don't try to do the usual MS SQL backups - let TFS handle the backups.
Git is very popular right now and can be used instead of TFS for source control, but TFS can integrate with Git. Git has more of a learning curve than TFS, IMO.
F A | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
It was used as an Application Lifecycle Management (ALM) system that takes care of all aspects of software development from planning, requirements gathering to coding, testing, deployment, and maintenance. Also as a Source Code Control(SCC), Bug Tracking, Project Management, and Team Collaboration platform.
SDLC Management (SDLC – Software Development Life Cycle):
  • Software Team Collaboration
  • Source Code Management
  • Supports Agile, Scrum, CMMI
  • Bug Tracking
  • Integrated Test Tools
  • Automated Builds
  • SDLC Management (SDLC – Software Development Life Cycle).
  • Software Team Collaboration.
  • Supports Agile, Scrum, CMMI.
  • Bug Tracking.
  • Reporting
  • Code integration
  • Project Management integrations
Team Foundation Server (TFS), provided by Microsoft, provides you a wide array of collaborative software development tools that integrate with your IDE providing secure version control, extensible integrations, agile tooling among many others. You can set up an on-premise version of TFS or you can sign up for Visual Studio Team Services which is backed by Microsoft Azure if you don’t want the hassle of managing the infrastructure.
Brendan McKenna | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use the Azure Dev Ops server throughout the IT department of our organization. It is utilized by Business Analysts, Scrum Masters, Developers, and QA. We have Git integration enabled and it has been an awesome experience with its integration to our source code. I especially love the built-in ability in the latest version to perform source code wide string searches. This makes it exceptionally easy to find code references and delve into new areas quickly. Aside from source control, it is our UI interface for all of our SCRUM project management needs. We create all of our tasks on the work items board and it makes it easy to see the progress of the overall team. Overall it's just been a great experience and I can't think of any complaints.
  • Git integration has been fantastic.
  • Provides a convenient UI for managing the SCRUM process.
  • Built-in Code Review feature and completion policies.
  • I wish I could default to a specific dashboard on load.
Great for source control, project management, and code reviews. It is really critical to put in place code review policies with required reviewers before a pull request can ever be merged into a target branch. As a senior developer sometimes I feel this can be cumbersome but there have been a few instances where I have caught a major error in a pull request and was able to prevent the code from being merged.
Vaibhav Choksi | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Dell Technologies uses Team Foundation Server for managing multiple projects across the North America region and rolling out in all other regions. If you use Visual Studio for development, TFS, or its online equivalent VSTS, you can have a fairly seamless end-to-end integration. Out of the box, it provides code management, testing, work hierarchy in agile formats, automated build, and deployment.

Dell manages source code, project reporting, engineering progress tracking and release management for agile software development. Microsoft TFS is also leveraged by the Product Management group to define and manage product requirements and managing the technical backlog. TFS really makes it easier to perform an end-to-end integration, reporting, tracking, code management, automated build, and deployment, etc.
  • TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
  • It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
  • It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
  • TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
  • Development in branches is hard to achieve and TFS has a room for improvement.
  • Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
Team Foundation Server is well suited in product management
  • Easier to build a technical backlog.
  • Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
  • Make a Product Manger's and engineering teams' life easier in meeting and tracking.
  • Project managers can easily track the work and create reporting.
Vinicius Lima | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server in the Information Systems Department in our company. All developers have access to Team Foundation Server to do code versioning. We use it integrated with Visual Studio to check-in and check-out our projects' code. We also use the web interface to navigate between code versions and to manually download code when necessary.
  • Integration with Microsoft products, like SharePoint, IIS, Visual Studio
  • Users are able to access via desktop client, web browser and through Visual Studio
  • Code version control
  • Bad UX and UI in the web interface
  • Merging code is a very hard task
  • Development in branches is also hard to achieve
  • Not so easy to upgrade server version
TFS is well suited to developers and teams that work with Microsoft technologies and products. For other scenarios, alternatives like Git can deliver more powerful and reliable features. Also, developing software in branches is very difficult, as well as merging code. These tasks needs to be carefully planned to avoid broken code and headaches in your company.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server to manage manage almost all the projects and application packages. Team Foundation Server makes it easy for us to have good control of all the progress and it really helps in managing the whole release process even if a lot of developers and many teams are involved.
  • The environment is easy to use.
  • It is very easy to track progress of various work items.
  • Project management is made really easy.
  • There is no ability to work offline.
  • There is a learning curve involved which is little hard to get when you are using the tool for the first time
  • The UI can be little more organized.
Team Foundation Server is specifically very useful for bigger teams which have a lot of developers and organizations with a lot of parallel team working on similar projects. It helps to keep track and manage the overall project well. I don't think of an alternative which is as powerful as TFS
Lavanya Elluri | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Team Foundation Server is used for version control of Microsoft .net applications, SSIS, SSRS. Also, TFS is used for tracking tasks, bugs and change requests.
  • Version Control
  • Track Bugs, Change Requests, Tasks
  • Compare versions of SSIS can be improved
  • Merging of the SSIS Code can also be improved
Team Foundation Server is a very a very good tool when you are using with Visual Studio. It's very easy to check in/check out the code to the Team Foundation Server. One can easily check the Task, Bugs and any change request items very easily from the Visual Studio. One can also check this items directly on the web browser as well.
Markus Hopfenspirger | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server as Source Control Managment System and for automated Builds and Tests. We don't use the WorkItem System of Team Foundation Server. We Used it a couple of years ago, but it was to complicated. Right now we just use Trello with a Scrum AddOn for Task and Backlog Planning. Right now only our Developers are using Team Foundation Server.
  • I like the Team Foundation Source Control Management much more compared to other Systems like GIT, because:
  • - Perfect Integration into Visual Studio
  • - Easy and direct checkout/check-in
  • - Perfect branching and merging
  • - Workflow Support with autmated Reminders
  • The Build System is just great. Since Version 2017 its very easy to integrate self made tools into the build process.
  • Easy Managament of Users and User Rights.
  • Team Foundation Server could be improved in the Task and Backlog Managment for smaller Teams. E.G.: It's hard to quickly write down Tasks during a meeting because you have to fill in lots of Fields per WorkItem. It is hard to push the Items around.
Well, as said before. I like TFS for Source Control and automated Builds and Testing, but it could be improved in the area of Task Management.
Luca Campanelli | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
In my organization Team Foundation Server is used to better manage all projects and application packages. Having several developers in place and having to work on multiple projects Team Foundation Server allows you to have complete control of all developments and to manage independently and with order every release and every package developed without loss of data or misalignments.
  • No data loss
  • Multiple deployments
  • Deployment without problems of versions
  • You must avoid getting stuck with check-in
  • Developers must avoid overwriting
  • The developers must be at minimum coordinated among themselves during the developments
if you are a development company or you work in a company with continuous developments it is certainly advisable to create a server dedicated to Team Foundation Server, surely you will have fewer problems in the deployment phase and you can always keep all the versioning of your software or your objects under control. Also, rollback in emergencies can be easily managed without losing too much time.
Brian Willis | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use it for our software development team. Team size is 8. It is being used as source control for .NET applications and as a continuous integration server. It is being used on site and also by our offshore partner developer team in Mexico. It helps us track versioning and collaborate with the peace of mind that we control the code.
  • Continuous integration when the team is using azure is really easy.
  • It's fairly intuitive to use.
  • Azure or IIS deployment is very easy.
  • The project management/scrum piece is hard to learn.
  • The Wikipedia functionality it provides isn't very useful for lack of features.
  • It takes a REALLY long time to check in a large number of newly added files.
  • If your file paths get too long, TFS gives you errors.
Team Foundation Server (TFS) is suited for anyone working in .NET. It's not appropriate otherwise. It's really as simple as that I think.

You could use some other source control with .NET but it integrates so well with the rest of the Microsoft family and is so reasonably priced, there'd be no need to.
Rich Mephan | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Team Foundation Server (TFS) is used by the development and test teams at Peppermint Technology. It is used for management of our source code and we also take advantage of the automated build functionality. We also use it for storing all of our release user stories, tracking enhancements and bugs as well as taking advantage of the project management tools to support our agile development process.
  • Work Item tracking - The ability to define the flow of your work items to match your development/test process is really valuable
  • Version Control - The ability to easily track changes between every checked in version of source code can be a life saver
  • Project Management - The project management dashboards showing things like burndown enables us to easily track whether we are on target for a release
  • Integration between our help desk system and TFS was possible but not as easy as I would expect considering both are Microsoft products
  • Advanced reporting for dashboards could be made easier
TFS is a really good tool for managing small to medium-sized development teams. The ability to customize it to suit your own processes means it should be suitable for any business, though I have to confess I do not have any experience of using it within a large enterprise sized development team split across disparate locations.That said we do have developers spread across the UK and they manage to work remotely with no problems at all.
Peter Anderson BEng MCSA | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server as a hub for our in-house software development. It allows the development team to centralise software issues, feature requests and testing.

Apple Trailer Download:

  • Source code management - Team Foundation Server handles our source code and makes examining check-ins and changes nice and easy.
  • Project Management - Keeping the thousands of feature requests and bug submissions under control and in the right place is simple enough in TFS.
  • Administration - As with most Microsoft products, administration is not a difficult affair. Familiar interfaces and tight integration with other Microsoft products make most tasks intuitive.
  • Web interface - While the web interface is certainly very feature rich, there's just no substitute for a good desktop interface sometimes. The test side has Microsoft Test Manager as a desktop application counterpart, but almost everything else is done via the website. Some project management tasks could be simpler in a desktop environment.
For a software development team, Team Foundation Server definitely ticks a lot of boxes. We use the Scrum methodology and Team Foundation Server enables us to manage current sprints and plan for future sprints. Even for 'pet projects' that some developers have, Team Foundation Server is a useful tool to submit their code for archiving and creating tasks to work on those projects.
October 26, 2017

Is TFS the right tool?

Erik Sheafer | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We are using TFS in our software division as a source control for code and DB objects. It allows us most importantly to keep a history of our code. Secondly, we can do deploys from this environment out to our many environments.
  • TFS has an excellent interactive UI for all users to make source control easy to use.
  • TFS has the backing of a major company, Microsoft. Updates and the way it is used gets regular updates.
  • TFS integrates into Visual Studio.
  • TFS has many tools for many different areas in the development life cycle.
  • There is no real ability to work offline. You need to be actively connected to it in order to see history.
  • Having many hands in the same project/file can cause conflicts that can be hard to resolve.
  • having a "master" branch is difficult in TFS, it can be done but it is slow and cumbersome and not an intuitive process.
I think if you work in a Microsoft exclusive environment, this is the tool for you. If you are in an arena where you might have C#, Java, or Python other tools might be better suited to your needs. TFS can be very costly but if it is instituted correctly with RM tools, it can be a wonderful thing. If you are a small shop use a free source control.
April 13, 2017

TFS = meh

Score 5 out of 10
Vetted Review
Verified User
Incentivized
We use team foundation server for source control.
  • Project management
  • Scrum
  • Integration with visual studio
  • Not a user friendly implementation of Git
  • TFS version control is not widely used in favor of Git
Using visual studio to manage source code instead of GitHub out bitbucket
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use it across the organization. We use TFS to manage projects beginning with the Business recording requirements, rating them by Priority and approving. IT utilizes TFS for managing Projects, versioning of code, Management of Test scripts. Utilizing the tool allows us full traceability.
  • Tractability, Code to defects, Test cases to Requirements
  • Metrics - Reworks on development, test cases to change, Defect by root cause
  • Single source for all to pull data, business and IT
  • Simplify automation testing, too much repetitive code with recording
  • Easier access to Code reviews - our development team struggles with this
  • Shelving and un-shelving details - development struggles in this area
[Team Foundation Server is well suited for] Agile - Kanban boards [make it] simple and easy to see progress. Shared queries allow for all to see information, centralizing communication. [It is also well suited for] Managing projects to preventing scope creep. Provides full tractability to ensure testing covers requirements, tree queries allow export of test coverage or lack there off. The tool provides collaboration between Development and QA with the trace data and log files gathered as a test case is being executed.
Erin Hinnen | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Team Foundation Server (TFS) is being utilized by many different departments within our organization. We personally use it to track tasks, user stories, bugs, releases, and test cases. Developers associate specific check-ins with bugs/user stories within TFS which, when pushed to our staging environments, are then assigned to QA/UAT for review. User stories and bugs are tracked as release scope for regular releases. The ability to associate releases/user stories/bugs in many different scenarios is priceless. It allows us to create different metrics/queries to measure success and potential failure, as well as to analyze what went well or what went wrong. TFS can be confusing for those new to the field or those who are older and used to other programs, but once the learning curve is achieved, the user tends to take well to the program.
  • Field customization is a feature TFS has that I particularly like. We have a very specialized customization of TFS running so that I can query for specific iteration/release paths that are relevant to our metrics. We also utilize a unique workflow structure for bugs and user stories as the process from creation to close is unique within our company.
  • TFS does their web view really well, especially with newer versions of the product. Often times, I feel that very little is lacking when I am logged into the web view of TFS. I am able to bulk edit items in the newer version of TFS, and at my old job we even set up the ability for QA to push checked in code to stage environments through TFS.
  • Finally, I feel TFS does a very good job of keeping historical track of actions performed to tickets. If someone has edited a ticket in any way, I can review and identify who made the change and when. This helps give me context when a developer contacts me to ask me a question related to the wording of a ticket. This also helps hold people accountable if tickets are written incorrectly or incompletely and prevents people from passing blame to others.
  • The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
  • VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
  • Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.
TFS is well suited for a team looking for structured requirements, projects, test cases, bugs, user stories, etc. It works well for planning things out and coordinating with others to see the "bigger view". TFS is great in scenarios where paper trails and other auditable data is needed to keep people in check and accountable. The search and query functionality allows users to search for past issues that may have been resolved previously and have crept back, and can provide history and context surrounding project functionality/decisions. TFS might not work as well for a team truly looking for a scrum experience. Although my companies have both claimed scrum, they both planned out releases at least a few weeks in advance. If you're changing things on a daily basis it might not be as great of a tool.
Return to navigation